home *** CD-ROM | disk | FTP | other *** search
- Path: fc.hp.com!news
- From: koren@hpsrk.fc.hp.com (Steve Koren)
- Newsgroups: comp.sys.amiga.applications
- Subject: Re: MUI
- Date: 05 Mar 1996 12:03:34 -0700
- Organization: HP Fort Collins Site
- Sender: koren@hpsrk.fc.hp.com
- Message-ID: <oj6vikjbbw9.fsf@hpsrk.fc.hp.com>
- References: <4h22lr$1d8@ns.hookon.be>
- <singh-0404952044330001@pool5-028.wwa.com>
- <4hdstb$2aj@ringer.cs.utsa.edu> <4hi0ej$906@macondo.dmu.ac.uk>
- NNTP-Posting-Host: hpsrk.fc.hp.com
- In-reply-to: hcm94rp2@dmu.ac.uk's message of Tue, 05 Mar 96 23:13:58 GMT
- X-Newsreader: Gnus v5.0.9
-
-
- hcm94rp2@dmu.ac.uk (Richard Perrott) wrote:
-
- > Also since MUI and its classes have so many data stored in codes hunks
- > I can't use VMM for a lot of the data parts, since MUI code and
- > applications I can't use VMM for a lot of the data parts, since MUI
- > code and applications won't tolerate being in virtual memory.
-
- MUI applications "tolerate" VMM just fine. I have *all* the MUI apps I
- use in my allow list for VMM for both code and data. It works fine,
- even under fairly heavy swapping.
-
- Also: storing data in code hunks has no bearing on whether or not the
- program can be used with VMM.
-
- - steve
-